home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
bbs_game
/
sdl212x.zip
/
HELP.FIL
< prev
next >
Wrap
Text File
|
1996-05-15
|
11KB
|
314 lines
STARDOCK LOCO HELP.FIL
Stardock Loco 1995-1996 Copyright, Aaron Alanen
------------------------------------------------------------------------
This is the HELP file! Make sure you read:
***SYSOP!!.DOC***
This file includes:
Simple Help, Modes of Operation (local, door), Scripting Information,
IGM information and locations, Support Info.
Additional multi-node help is at the bottom of the file.
Any bug reports would be appreciated at the addresses at the end of
the file. Includes the number for the support BBS.
A Maximus/2 help file is on line at the support bbs.
------------------------------------------------------------------------
SIMPLE HELP:
------------------------------------------------------------------------
Q:
Error message appears:
Critical Error [OpenDoors]: Unable to read door information (drop) file.
A:
What this means: Stardock Loco cannot find the door file specified by the
path that you are giving it. It's not there!
What to do: Check the path in your batch file that you are using for
the door. Make sure that it complies with the description
given below in the different modes of operation section.
Q:
Stardock Loco locks up after the initial screen:
A:
This happened to a lot of people at first. Make sure your
locked baud rate is the same for your system, modem, fossil
driver, and everything else you've got running! If
it still occurs, use the custom configuration file nodex.cfg
and set up your game using the directions in there.
Also, you may try letting your bbs system swap to disk, and
enable disk swapping.
Q:
I keep getting sharing violations! Help!!
A: Make sure you have share.exe loaded on your system.
Network Problems: If you have your system on a network, make sure
that the map that you have set is correct for the file
path. If it still doesn't respond, try copying the door
file to another directory on an unmapped drive before you
run the door. Then give the door the new path to the
copy of the door file.
If that doesn't work, try running it off a node that isn't
on the network. Just see if it will work.
Other help: If your system supports it, give it the path to a
different type of door file such as DOOR.SYS or DOORINFO.FIL
Stardock Loco can't find a file:
Somehow one of the files was deleted. If it is the player.lst
try to use the backup file player.bak, and rename it to
the player.lst. Any other file, just make a blank text file,
and name it the name of the missing file.
Or, reinstall the game, or download the whole package again.
-------------------------------------------------------------------------
Different modes of operation for Stardock Loco:
-------------------------------------------------------------------------
sdl212 /l Local mode for the sysop. The sysop can play the
game, or any player can play the game from local
mode. The game will ask for the players name at
the initial screen.
sdl212 -d c:\BBS\ Normal configuration to use the game. Reads the
DOOR.SYS, CHAIN.TXT, DOORINFO.FIL From the command
line. Should work without a problem. If not, use
the custom.cfg file.
Example batch file, for a Wildcat! System:
d:
cd\doors\sd
sdl212 -d d:\wildcat\wcwork\node%wcnodeid%\
cd\wildcat
exit
sdl212 /c [filename]
Custom configuration for non-standard BBS's and
for those having a problem running in normal mode.
Additional sysop options can be created from the
Custom.cfg file. Use it if you like. Or not at
all! It is not crucial to the game, and the settings
are ignored unless the /c option is used.
sdl212 -?
-HELP
-h will all bring up the settings that can be put
directly on the command line. You may put as
many command line options as you wish. Example:
sdl212 -PORT 1 -NOFOSSIL -IRQ 2
If you cannot get Stardock Loco to run using the the above settings,
try using the custom configuration file. The file is named custom.cfg.
Follow the short directions in the file, and run Stardock Loco like the
following:
sdl212 /c [filename]
See the custom.cfg file for more information.
This will force Stardock Loco to read all information about your system
from the configuration file. Before you try this, double check the path
that you have for Stardock Loco.
-------------------------------------------------------------------------
IGM Expansion Module Information:
-------------------------------------------------------------------------
Programmers can create IGM's for Stardock Loco. Expect to see numerous
versions to add to your game. If you wish, you can put the sd_devlp.zip
into your file base for your programming members.
A programmer needs the following files:
sd_devlp.txt <-programming info
module.c <-source code
Run SD_DEVLP.BAT to automatically zip all the files necessary
if you wish to. Creates the sd_devlp.zip.
* There are 2 types of IGM's that can be added.
The first is run by Stardock Loco without any installation needed.
The first two letters of it's name must be one of the following:
up*.exe <-upstairs at Terran Pete's
dn*.exe <-downstairs at Terran Pete's
nd*.exe <-from a player's ship
Example: upMYIGM.exe <-will run from Terran Pete's upstairs.
New Additions to the core:
Sickbay: sb??????.exe
WeaponShop: ws??????.exe
ArmorShop: as??????.exe
Terran Petes: tp??????.exe
Sleeping Pods: sp??????.exe
Bank: bk??????.exe
Nehru's Arena: na??????.exe
Other Aliens: oa??????.exe
If you are curious as to what will happen, rename roid.exe to bkroid.exe and
go to the bank. The Asteroid will appear instead.
These drop in IGM's cannot be put into their own directories.
5 others can be run from the Favrie Colony.
They are:
1fc*.exe
2fc*.exe <-the number makes them run from the corre-
3fc*.exe sponding slot on the colony's New Developments
4fc*.exe menu.
5fc*.exe
These require descriptions that can be typed into a text file.
You or the writer of the module have 50 characters.
The description files are the following:
1fc*.dsc
2fc*.dsc
3fc*.dsc <-description for corresponding slot. See
4fc*.dsc sd_devlp.txt for changing colors in the
5fc*.dsc description.
Example: 1fcJung.exe <-executable for first slot in Colony.
1fcJung.dsc <-description for first slot in Colony.
If you put one of these in your Stardock Directory, the game will run it
automatically. NOTE: If you have two with the same first letters in the
directory, it will run the *first* one it finds. You can always rename the
one you don't want in the special location, and use SD_ADD.EXE to make it
a regular module as described below.
Regular IGMs:
These are run from the ShipYards under the <O> Other Places menu.
they can have any name that is created by the third party. Hopefully
they will have included an install utility to install it, but if not,
use SD_ADD.EXE to add it to the MODULE.LST and it will work fine.
These can be put into their own directories.
----------------
You will find as you get more modules, that you may have to rename the files
or executables to put them into the correct spot in the game. However, you
can customize your game and put them wherever you please.
-------------------------------------------------------------------------
Scripting Information:
-------------------------------------------------------------------------
If a user wishes to write a script for Stardock Loco, they can without knowing
a programming language. Included in the zipped package is an editor that can
be used to write the scripts. These are different than IGM's or expansion
modules because they are accessed differently, and do not run independantly
of Stardock Loco.
What they need:
sdcreat1.exe <- the editor for writing the script
sdcreate.txt <- how to write the scripts
scrphelp.txt <- additional help for the script writer
trade.ans <- example ansi screen
trade.qst <- example quest
artifact.ans <- example ansi screen
artifact.qst <- example quest
sample.ans <- example ansi screen
sample.qst <- example quest
Run SCRIPT.BAT to automatically zip all these files into a zip file called
sdcreat1.zip.
If you have a member that creates a quest, you will have to put it into the
SCRIPT.LST by running SD_ADD.EXE. Follow the short directions for adding
the path and the description of the quest.
Shower.zip has been released by Bob Miller of Havasu, Az. You can get it
from the support bbs or from my web site:
http://www.starlink.com/~alanen
----------------------------------------------------------------------------
Additional Multi-node Help (3/6/96) Working in the .bat cave...
----------------------------------------------------------------------------
Multi-node wildcat batch file (3 nodes):
IF %WCNODEID%==0 GOTO RUN1
IF %WCNODEID%==1 GOTO RUN1
IF %WCNODEID%==2 GOTO RUN2
IF %WCNODEID%==3 GOTO RUN1
:RUN1
d:
cd\doors\sd
sdl212 -d d:\wildcat\wcwork\node%wcnodeid%\
ren sd_list.ans bull125.bbs
move d:\doors\sd\bull125.bbs d:\wildcat\bull
cd\wildcat
exit
REM For node 2, uses a node2.cfg file for non-standard irq settings:
:RUN2
D:
CD\DOORS\SD
sdl212 /C node2.cfg
REM sd_list.ans is the ansi scores list created by the game.
REN SD_LIST.ANS BULL125.BBS
MOVE D:\DOORS\SD\BULL125.BBS D:\WILDCAT\BULL
CD\WILDCAT
EXIT
=============================================================================
Any additional questions can be sent to me at the following addresses:
----------------------------------------------------------------------------
The support BBS for new versions of Stardock Loco is the Sherwood Forest BBS.
This BBS is run by a friend of mine, John Myers, aka Little_john.
The number is: (602) 876-0013.
To access the file and message areas for Stardock Loco,
use the following log-in:
First Name: Stardock
Last Name : Loco
Password : Support
My name, if you forgot, is Aaron Alanen. I can also be reached by i-mail/e-mail
at alanen@mail.hvs.com (Rock Garden BBS, Phoenix, AZ)
Other ways to reach me:
MajorNet: notme atall@rok
The Stardock Loco Homepage is located from a link from the Sherwood Forest
BBS Homepage on the (ugh!) WWW: http://www.starlink.com/~jam
Or snail:
Aaron Alanen
6502 E. Vernon
Scottsdale, AZ 85257-1140
USA.
See the ORDER.FRM to get information on registering Stardock Loco!
Thanks for reading this far!
---End of Help File---